Skip to content

Fix Issue #2614 - changed the publishing url for Python docs#2615

Closed
a-akimov wants to merge 1 commit into
modelcontextprotocol:mainfrom
a-akimov:fix-2614-doc-url
Closed

Fix Issue #2614 - changed the publishing url for Python docs#2615
a-akimov wants to merge 1 commit into
modelcontextprotocol:mainfrom
a-akimov:fix-2614-doc-url

Conversation

@a-akimov
Copy link
Copy Markdown

Motivation and Context

Fixing issue #2614 to make sure the link from MCP Docs SDKs page is not broken anymore and that Python docs are published to the right URL:
https://py.sdk.modelcontextprotocol.io/

How Has This Been Tested?

Since I don't have publishing rights in this project, I tested on another project.

Breaking Changes

No

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Since the docs are published manually for the Python SDK, this change will require one of SDK maintainers with sufficient rights to publish docs to the new URL.

@BossChaos

This comment was marked as abuse.

@BossChaos

This comment was marked as abuse.

maxisbey added a commit that referenced this pull request May 18, 2026
…tifact

Build both v1.x and main into a single Pages artifact (v1 at /, v2 at
/v2/), deployed via actions/deploy-pages on push to either branch. This
fixes the 404 at the custom domain (which DNS already points at GitHub
Pages but the repo never claimed) and stops the two branches from
overwriting each other's docs on release.

The legacy mkdocs gh-deploy path (docs-publish job in publish-pypi.yml
and the manual workflow) is removed; the gh-pages branch can be deleted
once the new deploy is confirmed working.

Closes #2614. Supersedes #2615.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants